Release 10.1A: OpenEdge Data Management:
Database Administration

PROUTIL IDXCOMPACT qualifier

Performs index compaction online.

proutil db-name -C idxcompact [ owner-name.]table-name.index-name [ n ]

Parameters

db-name

Specifies the source database name.

owner-name

Specifies the owner of the table containing the data you want to dump. You must specify an owner name unless the table’s name is unique within the database, or the table is owned by PUB. By default, Progress 4GL tables are owned by PUB.

table-name

Specifies the source table containing the source index to be compacted.

index-name

Specifies the source index to be compacted.

n

Specifies the degree of index compaction. You can specify an integer >=50 and <=100. The default value is 80. If you do not specify n, 80 is used.

Notes

Index compaction is recommended when the PROUTIL IDXANALYS utility indicates that space utilization of an index is reduced to 60% or less. Index compaction increases space utilization of the index block to the compacting percentage specified by n.
Performing index compaction reduces the number of blocks in the B-tree and possibly the number of B-tree levels, which improves query performance.
The index compacting utility operates in phases:
Phase 1 — If the index is a unique index, the delete chain is scanned and the index blocks are cleaned up by removing deleted entries.
Phase 2 — The nonleaf levels of the B-tree are compacted starting at the root working toward the leaf level.
Phase 3 — The leaf level is compacted.
PROUTIL IDXCOMPACT can be run either online or offline.
In addition to compacting an index, this utility clears dead entries left after entries have been deleted from unique indexes.
Because index compacting is performed online, other users can use the index simultaneously for read or write operation with no restrictions. Index compacting only locks 1 to 3 index blocks at a time, for a short time. This allows full concurrency.
The IDXCOMPACT utility does not lock any record or table.
No other administrative operation on the index is allowed during the compacting process.
In rare cases where the required percentage of compaction is very high, the compacting percentage might not be reached. Repeating the compacting process a second time might obtain better results.
See Chapter 14, "Maintaining Database Structure," for a description of how to monitor the progress of this utility using the _UserStatus virtual system table (VST).